Method and apparatus for storing user selected video content

ABSTRACT

A method and apparatus for enabling registered users to select and purchase video sessions from a network to be viewed from any video display devices connected to the network are disclosed. Specifically, these purchased video sessions can be stored within the network and accessed from any viewable display device connected to any video endpoint device at any time upon the users&#39; request. In one embodiment, the stored video sessions can be downloaded and recorded onto a recording medium for future use.

This application is a continuation of U.S. patent application Ser. No.11/258,460, filed Oct. 24, 2005, which is currently allowed and isherein incorporated by reference in its entirety.

The present invention relates generally to communication networks and,more particularly, to a method and apparatus for storing user selectedvideo content in communication networks, e.g., packet networks such asService over Internet Protocol (SoIP) networks.

BACKGROUND OF THE INVENTION

As extremely high bandwidth access networks become more accessible toresidential subscribers, they enable service providers of these networksto integrate voice, video, and data providing more convenience for endcustomers and creating new service opportunities. Due to themulti-service nature of these new services, networks need to provideadditional functionalities to end customers to support integratedcontrol of these different types of services. For instance, consumersincreasingly desire more personalized video content through on demand orpay per view video services. However, one limitation of these videoservices is that the selected content can only be displayed on a displaydevice connected to a video endpoint device through which the videosession order was placed. This is extremely inconvenient to users whohave multiple video endpoint devices and do not want their selectionlimited to be viewed on only one such device.

Therefore, a need exists for a method and apparatus for storing userselected video content in a packet network, e.g., a SoIP network.

SUMMARY OF THE INVENTION

In one embodiment, the present invention enables a method to allowregistered users to select and purchase video sessions from a network tobe viewed from any video display devices connected to the network.Specifically, these purchased video sessions can be stored within thenetwork and accessed from any viewable display device connected to anyvideo endpoint device at any time upon the users' request. In addition,in one embodiment, the stored video sessions can be downloaded andrecorded onto Digital Versatile Discs (DVD) for future use.

BRIEF DESCRIPTION OF THE DRAWINGS

The teaching of the present invention can be readily understood byconsidering the following detailed description in conjunction with theaccompanying drawings, in which:

FIG. 1 illustrates an exemplary Voice over Internet Protocol (VoIP)network related to the present invention;

FIG. 2 illustrates an exemplary Service over Internet Protocol (SoIP)network related to the present invention;

FIG. 3 illustrates an example of storing user selected video content ina packet network, e.g., a SoIP network, of the present invention;

FIG. 4 illustrates a flowchart of a method for storing user selectedvideo content in a packet network, e.g., a SoIP network, of the presentinvention;

FIG. 5 illustrates a flowchart of a method for accessing user purchasedvideo content in a packet network, e.g., a SoIP network, of the presentinvention; and

FIG. 6 illustrates a high level block diagram of a general purposecomputer suitable for use in performing the functions described herein.

To facilitate understanding, identical reference numerals have beenused, where possible, to designate identical elements that are common tothe figures.

DETAILED DESCRIPTION

To better understand the present invention, FIG. 1 illustrates acommunication architecture 100 having an example network, e.g., a packetnetwork such as a VoIP network related to the present invention.Exemplary packet networks include Internet protocol (IP) networks,asynchronous transfer mode (ATM) networks, frame-relay networks, and thelike. An IP network is broadly defined as a network that uses InternetProtocol to exchange data packets. Thus, a VoIP network or a SoIP(Service over Internet Protocol) network is considered an IP network.

In one embodiment, the VoIP network may comprise various types ofcustomer endpoint devices connected via various types of access networksto a carrier (a service provider) VoIP core infrastructure over anInternet Protocol/Multi-Protocol Label Switching (IP/MPLS) based corebackbone network. Broadly defined, a VoIP network is a network that iscapable of carrying voice signals as packetized data over an IP network.The present invention is described below in the context of anillustrative VoIP network. Thus, the present invention should not beinterpreted to be limited by this particular illustrative architecture.

The customer endpoint devices can be either Time Division Multiplexing(TDM) based or IP based. TDM based customer endpoint devices 122, 123,134, and 135 typically comprise of TDM phones or Private Branch Exchange(PBX). IP based customer endpoint devices 144 and 145 typically compriseIP phones or IP PBX. The Terminal Adaptors (TA) 132 and 133 are used toprovide necessary interworking functions between TDM customer endpointdevices, such as analog phones, and packet based access networktechnologies, such as Digital Subscriber Loop (DSL) or Cable broadbandaccess networks. TDM based customer endpoint devices access VoIPservices by using either a Public Switched Telephone Network (PSTN) 120,121 or a broadband access network via a TA 132 or 133. IP based customerendpoint devices access VoIP services by using a Local Area Network(LAN) 140 and 141 with a VoIP gateway or router 142 and 143,respectively.

The access networks can be either TDM or packet based. A TDM PSTN 120 or121 is used to support TDM customer endpoint devices connected viatraditional phone lines. A packet based access network, such as FrameRelay, ATM, Ethernet or IP, is used to support IP based customerendpoint devices via a customer LAN, e.g., 140 with a VoIP gateway androuter 142. A packet based access network 130 or 131, such as DSL orCable, when used together with a TA 132 or 133, is used to support TDMbased customer endpoint devices.

The core VoIP infrastructure comprises of several key VoIP components,such the Border Element (BE) 112 and 113, the Call Control Element (CCE)111, VoIP related Application Servers (AS) 114, and Media Server (MS)115. The BE resides at the edge of the VoIP core infrastructure andinterfaces with customers endpoints over various types of accessnetworks. A BE is typically implemented as a Media Gateway and performssignaling, media control, security, and call admission control andrelated functions. The CCE resides within the VoIP infrastructure and isconnected to the BEs using the Session Initiation Protocol (SIP) overthe underlying IP/MPLS based core backbone network 110. The CCE istypically implemented as a Media Gateway Controller or a softswitch andperforms network wide call control related functions as well asinteracts with the appropriate VoIP service related servers whennecessary. The CCE functions as a SIP back-to-back user agent and is asignaling endpoint for all call legs between all BEs and the CCE. TheCCE may need to interact with various VoIP related Application Servers(AS) in order to complete a call that require certain service specificfeatures, e.g. translation of an E.164 voice network address into an IPaddress.

For calls that originate or terminate in a different carrier, they canbe handled through the PSTN 120 and 121 or the Partner IP Carrier 160interconnections. For originating or terminating TDM calls, they can behandled via existing PSTN interconnections to the other carrier. Fororiginating or terminating VoIP calls, they can be handled via thePartner IP carrier interface 160 to the other carrier.

In order to illustrate how the different components operate to support aVoIP call, the following call scenario is used to illustrate how a VoIPcall is setup between two customer endpoints. A customer using IP device144 at location A places a call to another customer at location Z usingTDM device 135. During the call setup, a setup signaling message is sentfrom IP device 144, through the LAN 140, the VoIP Gateway/Router 142,and the associated packet based access network, to BE 112. BE 112 willthen send a setup signaling message, such as a SIP-INVITE message if SIPis used, to CCE 111. CCE 111 looks at the called party information andqueries the necessary VoIP service related application server 114 toobtain the information to complete this call. In one embodiment, theApplication Server (AS) functions as a SIP back-to-back user agent. IfBE 113 needs to be involved in completing the call; CCE 111 sendsanother call setup message, such as a SIP-INVITE message if SIP is used,to BE 113. Upon receiving the call setup message, BE 113 forwards thecall setup message, via broadband network 131, to TA 133. TA 133 thenidentifies the appropriate TDM device 135 and rings that device. Oncethe call is accepted at location Z by the called party, a callacknowledgement signaling message, such as a SIP 200 OK response messageif SIP is used, is sent in the reverse direction back to the CCE 111.After the CCE 111 receives the call acknowledgement message, it willthen send a call acknowledgement signaling message, such as a SIP 200 OKresponse message if SIP is used, toward the calling party. In addition,the CCE 111 also provides the necessary information of the call to bothBE 112 and BE 113 so that the call data exchange can proceed directlybetween BE 112 and BE 113. The call signaling path 150 and the callmedia path 151 are illustratively shown in FIG. 1. Note that the callsignaling path and the call media path are different because once a callhas been setup up between two endpoints, the CCE 111 does not need to bein the data path for actual direct data exchange.

Media Servers (MS) 115 are special servers that typically handle andterminate media streams, and to provide services such as announcements,bridges, transcoding, and Interactive Voice Response (IVR) messages forVoIP service applications.

Note that a customer in location A using any endpoint device type withits associated access network type can communicate with another customerin location Z using any endpoint device type with its associated networktype as well. For instance, a customer at location A using IP customerendpoint device 144 with packet based access network 140 can callanother customer at location Z using TDM endpoint device 123 with PSTNaccess network 121. The BEs 112 and 113 are responsible for thenecessary signaling protocol translation, e.g., SS7 to and from SIP, andmedia format conversion, such as TDM voice format to and from IP basedpacket voice format.

The network shown in FIG. 1 can be extended to become a SoIP networkthat supports multi-service applications including, but not limited to,video services. FIG. 2 illustrates a communication architecture 200having an example network, e.g., a packet network such as a SoIP networkrelated to the present invention. A SoIP network supports multi-serviceapplications including voice, data, and video services. In oneembodiment, a SoIP network that supports video services is describedbelow. In this SoIP network, voice services supported include, but arenot limited to, VoIP services; data services supported include, but arenot limited to, Instant Messaging (IM), electronic mail (email),internet access services, or any other IP based applications; and videoservices include, but are not limited to, Video on Demand (VoD),broadcast video, and video conferencing services.

A SoIP network that supports video services comprises an intelligentmulti-service endpoint device connected via packet access networks to aservice provider's SoIP core infrastructure employing Internet Protocol(IP) and/or Multi-Protocol Label Switching (MPLS) Protocols. Broadlydefined, a SoIP network is a network that is capable of carrying voice,video, and data signals as packetized data over an IP network. Thepresent invention is described below in the context of an illustrativeSoIP network that supports video services. Thus, the present inventionshould not be interpreted to be limited by this particular illustrativearchitecture.

Video endpoint device 232 and 233 are IP based intelligent multi-serviceendpoint device supporting voice, video, and data applications. Videoendpoint device 232 and 233 are signaling endpoints of applicationsessions, e.g. a VoIP session endpoint, an instant messaging endpoint,or a video session endpoint. In one embodiment, a video endpoint deviceis a standalone device that can be connected to home electronicappliances such as, but is not limited to, telephone 234 and 235, TV 236and 237, or Personal Computer (PC) 238 and 239. In another embodiment, avideo endpoint device can be integrated with a TV, a PC, or any homeappliances with a display.

The access networks are packet based. Packet based access networks 230and 231 use, but are not limited to, Frame Relay, ATM, Ethernet, IP, DSLor Cable broadband access network technologies to interconnect a videoendpoint device to a SoIP network that supports video services.

The core SoIP infrastructure that supports video services comprises ofseveral key components, such the Border Element (BE) 212 and 213, theCall Control Element (CCE) 211, SoIP related Application Servers (AS)214, Media Servers (MS) 215, Session Controller (SC) 241, Video ofDemand (VoD) Servers 242, Broadcast Servers (242), and Instant Messaging(IM) Servers 243. A BE resides at the edge of the SoIP coreinfrastructure and interfaces with customers endpoints over varioustypes of access networks. The functions supported by a BE include thosesupported by a BE as previously described in network 100 and FIG. 1. Inaddition, in a SoIP network that supports video services, a BE alsoserves as a gateway between a video endpoint device used by a subscriberand the SoIP core network that supports video services. All applicationsessions initiated by a SoIP subscriber must gain entry to the SoIP corenetwork via a BE. The functions supported by a CCE and a MS are the sameas those previously described in network 100 and FIG. 1. A SessionController (SC) resides within the SoIP infrastructure and is connectedto the BEs using an IP based signaling protocol such as, but is notlimited to, Session Initiation Protocol (SIP). A SC is responsible forsetting up all application session requests, such as VoIP call requests,video session requests, or data session requests, originated by acustomer within the network and interacts with, if necessary, theappropriate SoIP related AS in order to complete an application sessionthat requires certain service specific features originated by acustomer. A SC also keeps track of all sessions initiated by a customerfor session management and billing purposes as well. The functionssupported by a SoIP related AS include those supported by a VoIP AS aspreviously described in network 100 and FIG. 1. In addition, a SoIP ASalso supports all video specific application features. A VoD Server isresponsible for supporting video on demand video session requestsoriginated by a customer and sends the requested streaming videocontents, such as a movie, to the customer. A Broadcast Server isresponsible for supporting broadcast video session requested originatedby a customer and sends streaming broadcast video contents, such as TVchannels, to the customer. The VoD Server and the Broadcast Server sendsstreaming video contents to video endpoint devices using compressiontechnologies including, but are not limited to, Moving Picture ExpertsGroup (MPEG) 2, MPEG 4, MPEG 7, MPEG 21. An IM Server is responsible forsupporting IM applications involving multiple users. Instant Messagingis a form of electronic communication that involves immediate typed textcorrespondence between two or more users over the Internet who areonline simultaneously. IM is a text-based computer conference over theInternet between two or more people who are online at the same time.

In order to illustrate how the different components in a SoIP networkoperate to support video services, the following scenarios are used toillustrate how voice, data, and video sessions are setup between theSoIP network and a video endpoint. In one embodiment, a customer usingvideo endpoint device 232 at location A places a VoD session request tothe SoIP network that supports video services using TV 236. During thesession initiation, a setup signaling message is sent from videoendpoint device 232 to BE 212 using signaling path segment 250. BE 212will then send a setup signaling message, such as a SIP-INVITE messageif SIP is used, to SC 241 using signaling path segment 251. SC 241processes the session requests and forwards the request to theappropriate server for further processing. In this case, the request isa VoD session; therefore, the request will be forwarded to VoD Server242 using signaling path segment 252. SC 241 may interact with AS 214using signaling path segment 259 to verify customer's subscriptioninformation or to retrieve video specific applications or data in orderto complete the session request. Once the VoD session is verified, VoDServer 242 sends the requested VoD streaming contents to BE 212 usingdata path segment 262. BE 212 then forwards the requested VoD streamingcontents to video endpoint 232 using data path segment 260. Similarly, acustomer at location Z using TV 237 connected to video endpoint 233 canrequest a VoD session via SC 241 with streaming VoD contents sent by VoDServer 242. Note that a VoD server may be placed closer to end users ina packet access network to serve video endpoints in an alternativeembodiment.

In another embodiment, a customer using video endpoint device 232 atlocation A places a broadcast video session request to the SoIP networkthat supports video services using TV 236. During the sessioninitiation, a setup signaling message is sent from video endpoint device232 to BE 212 using signaling path segment 250. BE 212 will then send asetup signaling message, such as a SIP-INVITE message if SIP is used, toSC 241 using signaling path segment 251. SC 241 processes the sessionrequests and forwards the request to the appropriate server for furtherprocessing. In this case, the request is a broadcast video session for aparticular premium TV channel; therefore, the request will be forwardedto Broadcast Server 243 using signaling path segment 253. SC 241 mayinteract with AS 214 using signaling path segment 259 to verifycustomer's subscription information or to retrieve video specificapplications or data in order to complete the session request. Once thebroadcast session is verified, Broadcast Server 243 sends the requestedbroadcast video streaming contents to BE 212 using data path segment263. BE 212 then forwards the requested broadcast video streamingcontents to video endpoint 232 using data path segment 260. Similarly, acustomer at location Z using TV 237 connected to video endpoint 233 canrequest a broadcast video session via SC 241 with streaming broadcastvideo contents sent by Broadcast Server 243. Note that a Broadcastserver may be placed closer to end users in a packet access network toserve video endpoints in an alternative embodiment.

In another embodiment, a customer using video endpoint device 232 atlocation A places an IM session request to the video network using PC238. During the session initiation, a setup signaling message is sentfrom video endpoint device 232 to BE 212 using signaling path segment250. BE 212 will then send a setup signaling message, including loginand password information of the user, to SC 241 using signaling pathsegment 251. SC 241 processes the session requests and forwards therequest to the appropriate server for further processing. In this case,the request to sign on an IM session; therefore, the request will beforwarded to IM Server 244 using signaling path segment 254. SC 241 mayinteract with AS 214 using signaling path segment 259 to verifycustomer's subscription information or to retrieve IM specificapplications or data in order to complete the session request. Once theIM session is verified, IM Server 244 establishes the requested IM datapath to video endpoint 232 via BE 212 using data path comprising datapath segment 260 and 264. Similarly, a customer at location A using TV236 connected to video endpoint 232 or a customer at location Z using PC239 or TV 237 connected to video endpoint 233 can request an IM sessionvia SC 241 with IM functions provided by IM Server 244.

In another embodiment, a customer using video endpoint device 232 atlocation A places a VoIP session request destined to video endpointdevice 233 via the SoIP network that supports video services usingtelephone 234. During the session initiation, a setup signaling messageis sent from video endpoint device 232 to BE 212 using signaling pathsegment 250. BE 212 will then send a setup signaling message, such as aSIP-INVITE message if SIP is used, to SC 241 using signaling pathsegment 251. SC 241 processes the session requests and forwards therequest to the appropriate server for further processing. In this case,the request is a VoIP session for a call destined to a called party atlocation Z; therefore, the request will be forwarded to CCE 211 usingsignaling path segment 255. CCE may interact with AS 214 using signalingpath segment 259 to verify customer's subscription information or toretrieve VoIP specific applications or data in order to complete thesession request. The signaling flows to establish a VoIP call betweenvideo endpoint device 232 and 233 is similar to those describedpreviously in network 100 and FIG. 1. In one embodiment, the ApplicationServer (AS) functions as a SIP back-to-back user agent. Since BE 213needs to be involved in completing the call; CCE 211 sends another callsetup message, such as a SIP-INVITE message if SIP is used, to BE 213using signaling path segment 257. Upon receiving the call setup message,BE 213 forwards the call setup message, via packet access network 231 tovideo endpoint device 233 using signaling path segment 258. Videoendpoint device 233 then identifies telephone 235 and rings thattelephone. Once the call is accepted at location Z by the called party,a call acknowledgement signaling message, such as a SIP 200 OK responsemessage if SIP is used, is sent in the reverse direction back to the CCE211. After the CCE 211 receives the call acknowledgement message, itwill then send a call acknowledgement signaling message, such as a SIP200 OK response message if SIP is used, toward the calling party atlocation A using signaling path comprising signaling path segment 256and 250 via BE 212. In addition, the CCE 211 also provides the necessaryinformation of the call to both BE 212 and BE 213 so that the call dataexchange can proceed directly between BE 212 and BE 213. CCE 211 alsoprovides the call completion status of a VoIP call to SC 241. The callmedia path comprising media path segment 260, 261, and 265 areillustratively shown in FIG. 2. Note that the call signaling path andthe call media path are different because once a call has been setup upbetween two video endpoint devices, SC 241 and CCE 211 does not need tobe in the data path for actual direct data exchange.

As extremely high bandwidth access networks become more accessible toresidential subscribers, they enable service providers of these networksto integrate voice, video, and data providing more convenience for endcustomers and creating new service opportunities. Due to themulti-service nature of these new services, networks need to provideadditional functionalities to end customers to support integratedcontrol of these different types of services. For instance, consumersincreasingly desire more personalized video content through on demand orpay per view video services. However, one limitation of these videoservices is that the selected content can only be displayed on a displaydevice connected to a video endpoint device through which the videosession order was placed. This is extremely inconvenient to users whohave multiple video endpoint devices and do not want their selectionlimited to be viewed on only one such device.

To address this criticality, the present invention enables a method toallow registered users to select and purchase video sessions from anetwork to be viewed from any video display devices connected to thenetwork. Specifically, these purchased video sessions can be storedwithin the network and accessed from any viewable display deviceconnected to any video endpoint device at any time upon the users'request. In addition, in one embodiment, the stored video sessions canbe downloaded and recorded onto Digital Versatile Discs (DVD) for futureuse.

FIG. 3 illustrates an example 300 of storing user selected video contentin a packet network, e.g., a SoIP network, of the present invention. InFIG. 3, subscriber 371 purchases a video session (broadly covering anyimage sequence, e.g., a movie, a music video, a video of a musicalconcert, a video of a play, a video of a sports event and the like),from the network using TV 338 as a console. Through video endpointdevice 332, subscriber 371 sends the video purchase request to SC 341using flow 350. In turn, SC 341 finds out that the request is a videopurchase order and forwards the purchase request to VoD Server 342 usingflow 351 to be completed. Since the video session is a purchased movie,the network stores the purchased movie in VoD Server 342 for use bysubscriber 371 either immediately or at a later time.

When subscriber 371 is ready to view the purchased video session,subscriber 371 can use TV 338 to view the movie. A video session accessrequest is sent by subscriber 371 via video endpoint device 332 to SC.341 using flow 350. Video endpoint device 332 needs to be authorizedusing a set of correct user name and password to authenticate the accessto the purchased video session. Once authorized, the access request isforwarded by SC 341 to a VoD Server 342 using flow 351 for processing.In this case, VoD Server 342, upon receiving an instruction fromsubscriber 371, will send the purchased video session in streaming videoformat to TV 338 via video endpoint device 332 using flow 360.

Similarly, subscriber 371 can use TV 339 to view the movie. A videosession access request is sent by subscriber 371 via video endpointdevice 332 to SC 341 using flow 350. Video endpoint device 332 needs tobe authorized using a set of correct user name and password toauthenticate the access to the purchased video session. Once authorized,the access request is forwarded by SC 341 to a VoD Server 342 using flow351 for processing. In that case, VoD Server 342, upon receiving aninstruction from subscriber 371, will send the purchased video sessionin streaming video format to TV 339 via video endpoint device 332 usingflow 361. In addition, subscriber 371 can view the movie on both TV 338and TV 339 using flows 360 and 361 simultaneously if so desired.

Even though subscriber 371 purchases the movie through video endpointdevice 332, subscriber 371 can access the purchased movie via anyauthorized SoIP endpoint, such as video endpoint devices. For instance,in FIG. 3, subscriber 371 may use TV 337 as a console to view thepurchased movie via video endpoint device 333. A video session accessrequest is sent by subscriber 371 via video endpoint device 333 to SC341 using flow 352. Video endpoint device 333 needs to be authorizedusing a set of correct user name and password to authenticate the accessto the purchased video session. Once authorized, the access request isforwarded by SC 341 to a VoD Server 342 using flow 351 for processing.In that case, VoD Server 342, upon receiving an instruction fromsubscriber 371, will send the purchased video session in streaming videoformat to TV 337 via video endpoint device 333 using flow 362. In fact,subscriber 371 can request the movie to be simultaneously sent to TV 338and TV 339 via video endpoint device 332 using flows 360 and 361respectively and TV 337 via video endpoint device 333 using flow 362.Moreover, subscriber 371 can download the movie at any time via aregistered video endpoint device to a compatible user device, such as aDVD recorder, that will burn the purchased movie onto a DVD for laterviewing and archive purposes.

FIG. 4 illustrates a flowchart of a method 400 for storing user selectedvideo content in a packet network, e.g., a SoIP network, of the presentinvention. Method 400 starts in step 405 and proceeds to step 410.

In step 410, the method receives a video session purchase, e.g. arequest to purchase a movie, from a subscriber. The video sessionpurchase is received by a SC.

In step 420, the method completes the purchase and stores the purchasedvideo session in the network. The SC forwards the video session purchaseorder to a VoD Server for completion. The purchased video session willbe stored at the VoD Server and can be accessed by the subscriber fromthe VoD Server at any time after the purchase. The subscriber can accessto view the movie immediately or at a later time of convenience afterthe purchase. The method ends in step 430.

In one embodiment, a separate copy of the purchased video session isstored at the VoD Server. Namely, the purchased video session is notshared with other subscribers.

FIG. 5 illustrates a flowchart of a method 500 for accessing userpurchased video content in a packet network, e.g., a SoIP network, ofthe present invention. Method 500 starts in step 505 and proceeds tostep 510.

In step 510, the method receives an access request to access a purchasedvideo session from a subscriber. For example, the access request isreceived by a SC.

In step 520, the method checks if the access originates from anauthorized video endpoint device. If the access originates from anauthorized video endpoint device, the method proceeds to step 525;otherwise, the method proceeds to step 540. In one embodiment, a videoendpoint device is considered an authorized video endpoint device if thesubscriber sends the correct user name and password to authenticate theaccess to the purchased video session via that particular video endpointdevice. Once authorized, the access request is forwarded by the SC to aVoD server for further processing.

In step 525, the method establishes the purchased video session betweenthe VoD server and the subscriber. Namely, the SC forwards the videosession setup request to the VoD Server for processing.

In step 530, the method sends the purchased video session to one or moreauthorized video endpoint devices requested by the subscriber. The videosession associated contents are sent by the VoD Server. Each of theauthorized video endpoint devices may be equipped with one or more videodisplay devices. In addition, in one embodiment, an authorized videostream can be downloaded to a compatible user device, such as a DVDrecorder, to be archived for later use. The method ends in step 540.

FIG. 6 depicts a high level block diagram of a general purpose computersuitable for use in performing the functions described herein. Asdepicted in FIG. 6, the system 600 comprises a processor element 602(e.g., a CPU), a memory 604, e.g., random access memory (RAM) and/orread only memory (ROM), a module 605 for storing user selected videocontent, and various input/output devices 606 (e.g., storage devices,including but not limited to, a tape drive, a floppy drive, a hard diskdrive or a compact disk drive, a receiver, a transmitter, a speaker, adisplay, a speech synthesizer, an output port, and a user input device(such as a keyboard, a keypad, a mouse, and the like)).

It should be noted that the present invention can be implemented insoftware and/or in a combination of software and hardware, e.g., usingapplication specific integrated circuits (ASIC), a general purposecomputer or any other hardware equivalents. In one embodiment, thepresent module or process 605 for storing user selected video contentcan be loaded into memory 604 and executed by processor 602 to implementthe functions as discussed above. As such, the present process 605 forstoring user selected video content (including associated datastructures) of the present invention can be stored on a computerreadable medium or carrier, e.g., RAM memory, magnetic or optical driveor diskette and the like.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example only, and notlimitation. Thus, the breadth and scope of a preferred embodiment shouldnot be limited by any of the above-described exemplary embodiments, butshould be defined only in accordance with the following claims and theirequivalents.

What is claimed is:
 1. A method for storing video content in acommunication network, comprising: receiving, by a video on demandserver, a request to purchase a video session from a subscriber;processing, by the video on demand server, the request by storing thevideo session at the video on demand server in the communicationnetwork; and transmitting, by the video on demand server, the videosession stored at the video on demand server in the communicationnetwork that was purchased by the subscriber simultaneously from thevideo on demand server to a plurality of endpoints of the subscriberthat is used to view the video session while stored in the communicationnetwork via a streaming video format, where each endpoint comprises avideo display device, wherein each endpoint comprises an internetprotocol based intelligent multi-service endpoint device supportingvoice, video and data applications, wherein each one of the plurality ofendpoints accesses the video session over a different independentstreaming session directly from the video on demand server in thecommunication network.
 2. The method of claim 1, wherein thecommunication network is a service over Internet protocol network. 3.The method of claim 1, wherein the request is received via a sessioncontroller.
 4. The method of claim 1, wherein the transmittingcomprises: receiving an access request from the subscriber to view thevideo session; authenticating the access request using a user name and apassword to authorize the access request; and transmitting the videosession to the subscriber.
 5. The method of claim 4, wherein the accessrequest is received and authenticated via a session controller.
 6. Themethod of claim 1, wherein the video session is downloaded to arecording device to be recorded.
 7. A tangible computer-readable storagemedium storing a plurality of instructions which, when executed by aprocessor of a video on demand server, cause the processor to performoperations for storing video content in a communication network, theoperations comprising: receiving a request at the video on demand serverto purchase a video session from a subscriber; processing the request bystoring the video session at the video on demand server in thecommunication network; and transmitting by the video on demand serverthe video session stored at the video on demand server in thecommunication network that was purchased by the subscribersimultaneously from the video on demand server to a plurality ofendpoints of the subscriber that is used to view the video session whilestored in the communication network via a streaming video format, whereeach endpoint comprises a video display device, wherein each endpointcomprises an internet protocol based intelligent multi-service endpointdevice supporting voice, video and data applications, wherein each oneof the plurality of endpoints accesses the video session over adifferent independent streaming session directly from the video ondemand server in the communication network.
 8. The tangiblecomputer-readable storage medium of claim 7, wherein the communicationnetwork is a service over internet protocol network.
 9. The tangiblecomputer-readable storage medium of claim 7, wherein the request isreceived and authenticated by a session controller.
 10. The tangiblecomputer-readable storage medium of claim 7, wherein the transmittingcomprises: receiving an access request from the subscriber to view thevideo session; authenticating the access request using a user name and apassword to authorize the access request; and transmitting the videosession to the subscriber.
 11. The tangible computer-readable storagemedium of claim 10, wherein the access request is received andauthenticated by a session controller.
 12. The tangiblecomputer-readable storage medium of claim 7, wherein the video sessionis downloaded to a recording device to be recorded.
 13. An apparatus forstoring video content in a communication network, comprising: a video ondemand server comprising a processor, and a computer-readable medium,wherein the computer-readable medium stores a plurality of instructionswhich, when executed by the processor, cause the processor to performoperations, the operations comprising: receiving a request to purchase avideo session from a subscriber; processing the request by storing thevideo session at the video on demand server in the communicationnetwork; and transmitting by the video on demand server the videosession stored at the video on demand server in the communicationnetwork that was purchased by the subscriber simultaneously from thevideo on demand server to a plurality of endpoints of the subscriberthat is used to view the video session while stored in the communicationnetwork via a streaming video format, where each endpoint comprises avideo display device, wherein each endpoint comprises an internetprotocol based intelligent multi-service endpoint device supportingvoice, video and data applications, wherein each one of the plurality ofendpoints accesses the video session over a different independentstreaming session directly from the video on demand server in thecommunication network.
 14. The apparatus of claim 13, wherein thecommunication network is a service over internet protocol network. 15.The apparatus of claim 13, wherein the request is received andauthenticated by a session controller.
 16. The apparatus of claim 13,wherein the transmitting comprises: receiving an access request from thesubscriber to view the video session; authenticating the access requestusing a user name and a password to authorize the access request; andtransmitting the video session to the subscriber.
 17. The apparatus ofclaim 16, wherein the access request is received and authenticated by asession controller.
 18. The apparatus of claim 13, wherein the videosession is downloaded to a recording device to be recorded.